home *** CD-ROM | disk | FTP | other *** search
/ IRIX Base Documentation 2001 May / SGI IRIX Base Documentation 2001 May.iso / usr / share / catman / p_man / cat3n / t_snddis.z / t_snddis
Encoding:
Text File  |  1998-10-20  |  8.2 KB  |  133 lines
  1.  
  2.  
  3.  
  4. tttt____ssssnnnnddddddddiiiissss((((3333NNNN))))                                                      tttt____ssssnnnnddddddddiiiissss((((3333NNNN))))
  5.  
  6.  
  7.  
  8. NNNNAAAAMMMMEEEE
  9.      _tttt______ssss_nnnn_dddd_dddd_iiii_ssss - send user-initiated disconnect request
  10.  
  11. SSSSYYYYNNNNOOOOPPPPSSSSIIIISSSS
  12.      _####_iiii_ffff_dddd_eeee_ffff ______XXXX_OOOO_PPPP_EEEE_NNNN______SSSS_OOOO_UUUU_RRRR_CCCC_EEEE
  13.      _####_iiii_nnnn_cccc_llll_uuuu_dddd_eeee _<<<<_xxxx_tttt_iiii_...._hhhh_>>>>
  14.      _####_eeee_llll_ssss_eeee
  15.      _####_iiii_nnnn_cccc_llll_uuuu_dddd_eeee _<<<<_tttt_iiii_uuuu_ssss_eeee_rrrr_...._hhhh_>>>>
  16.      _####_eeee_nnnn_dddd_iiii_ffff
  17.  
  18.      _iiii_nnnn_tttt _tttt______ssss_nnnn_dddd_dddd_iiii_ssss _((((_iiii_nnnn_tttt _ffff_dddd_,,,, _ssss_tttt_rrrr_uuuu_cccc_tttt _tttt______cccc_aaaa_llll_llll _****_cccc_aaaa_llll_llll_))))_::::
  19.  
  20. DDDDEEEESSSSCCCCRRRRIIIIPPPPTTTTIIIIOOOONNNN
  21.      This function is used to initiate an abortive release on an already
  22.      established connection or to reject a connect request.  _ffff_dddd identifies the
  23.      local transport endpoint of the connection, and _cccc_aaaa_llll_llll specifies
  24.      information associated with the abortive release.  _cccc_aaaa_llll_llll points to a
  25.      _tttt______cccc_aaaa_llll_llll structure that contains the following members:
  26.  
  27.           _ssss_tttt_rrrr_uuuu_cccc_tttt _nnnn_eeee_tttt_bbbb_uuuu_ffff _aaaa_dddd_dddd_rrrr_;;;;
  28.           _ssss_tttt_rrrr_uuuu_cccc_tttt _nnnn_eeee_tttt_bbbb_uuuu_ffff _oooo_pppp_tttt_;;;;
  29.           _ssss_tttt_rrrr_uuuu_cccc_tttt _nnnn_eeee_tttt_bbbb_uuuu_ffff _uuuu_dddd_aaaa_tttt_aaaa_;;;;
  30.           _iiii_nnnn_tttt _ssss_eeee_qqqq_uuuu_eeee_nnnn_cccc_eeee_;;;;
  31.  
  32.      _nnnn_eeee_tttt_bbbb_uuuu_ffff is described in _iiii_nnnn_tttt_rrrr_oooo(3N).  The values in _cccc_aaaa_llll_llll have different
  33.      semantics, depending on the context of the call to _tttt______ssss_nnnn_dddd_dddd_iiii_ssss.  When
  34.      rejecting a connect request, _cccc_aaaa_llll_llll must be non-_NNNN_UUUU_LLLL_LLLL and contain a valid
  35.      value of _ssss_eeee_qqqq_uuuu_eeee_nnnn_cccc_eeee to identify uniquely the rejected connect indication to
  36.      the transport provider.  The _aaaa_dddd_dddd_rrrr and _oooo_pppp_tttt fields of _cccc_aaaa_llll_llll are ignored.  In
  37.      all other cases, _cccc_aaaa_llll_llll need only be used when data is being sent with the
  38.      disconnect request.  The _aaaa_dddd_dddd_rrrr, _oooo_pppp_tttt, and _ssss_eeee_qqqq_uuuu_eeee_nnnn_cccc_eeee fields of the _tttt______cccc_aaaa_llll_llll
  39.      structure are ignored.  If the user does not want to send data to the
  40.      remote user, the value of _cccc_aaaa_llll_llll may be _NNNN_UUUU_LLLL_LLLL.
  41.  
  42.      _uuuu_dddd_aaaa_tttt_aaaa specifies the user data to be sent to the remote user.  The amount
  43.      of user data must not exceed the limits supported by the transport
  44.      provider as returned in the _dddd_iiii_ssss_cccc_oooo_nnnn field of the _iiii_nnnn_ffff_oooo argument of _tttt______oooo_pppp_eeee_nnnn
  45.      or _tttt______gggg_eeee_tttt_iiii_nnnn_ffff_oooo.  If the _llll_eeee_nnnn field of _uuuu_dddd_aaaa_tttt_aaaa is zero, no data will be sent to
  46.      the remote user.
  47.  
  48.      This function resides within both the X/Open compliant _llll_iiii_bbbb_xxxx_nnnn_eeee_tttt and the
  49.      SVR4 compliant _llll_iiii_bbbb_nnnn_ssss_llll Network Services libraries.  Network Services
  50.      applications which require X/Open compliance must link-load with _----_llll_xxxx_nnnn_eeee_tttt.
  51.      Network Services applications which require SVR4 compliance must link-
  52.      load with _----_llll_nnnn_ssss_llll.
  53.  
  54.      On failure, _tttt______eeee_rrrr_rrrr_nnnn_oooo may be set to one of the following:
  55.  
  56.      _TTTT_BBBB_AAAA_DDDD_FFFF              The specified file descriptor does not refer to a
  57.                         transport endpoint.
  58.  
  59.  
  60.  
  61.  
  62.  
  63.                                                                         PPPPaaaaggggeeee 1111
  64.  
  65.  
  66.  
  67.  
  68.  
  69.  
  70. tttt____ssssnnnnddddddddiiiissss((((3333NNNN))))                                                      tttt____ssssnnnnddddddddiiiissss((((3333NNNN))))
  71.  
  72.  
  73.  
  74.      _TTTT_OOOO_UUUU_TTTT_SSSS_TTTT_AAAA_TTTT_EEEE          The function was issued in the wrong sequence.  The
  75.                         transport provider's outgoing queue may be flushed, so
  76.                         data may be lost.
  77.  
  78.      _TTTT_BBBB_AAAA_DDDD_DDDD_AAAA_TTTT_AAAA           The amount of user data specified was not within the
  79.                         bounds supported by the transport provider as returned
  80.                         in the _dddd_iiii_ssss_cccc_oooo_nnnn field of the _iiii_nnnn_ffff_oooo argument of _tttt______oooo_pppp_eeee_nnnn or
  81.                         _tttt______gggg_eeee_tttt_iiii_nnnn_ffff_oooo.  The transport provider's outgoing queue
  82.                         will be flushed, so data may be lost.
  83.  
  84.      _TTTT_BBBB_AAAA_DDDD_SSSS_EEEE_QQQQ            An invalid sequence number was specified, or a _NNNN_UUUU_LLLL_LLLL
  85.                         call structure was specified when rejecting a connect
  86.                         request.  The transport provider's outgoing queue will
  87.                         be flushed, so data may be lost.
  88.  
  89.      _TTTT_LLLL_OOOO_OOOO_KKKK              An asynchronous event has occurred on this transport
  90.                         endpoint and requires immediate attention.
  91.  
  92.      _TTTT_NNNN_OOOO_TTTT_SSSS_UUUU_PPPP_PPPP_OOOO_RRRR_TTTT        This function is not supported by the underlying
  93.                         transport provider.
  94.  
  95.      _TTTT_SSSS_YYYY_SSSS_EEEE_RRRR_RRRR            A system error has occurred during execution of this
  96.                         function.
  97.  
  98. SSSSEEEEEEEE AAAALLLLSSSSOOOO
  99.      _iiii_nnnn_tttt_rrrr_oooo(3N), _tttt______cccc_oooo_nnnn_nnnn_eeee_cccc_tttt(3N), _tttt______gggg_eeee_tttt_iiii_nnnn_ffff_oooo(3N), _tttt______llll_iiii_ssss_tttt_eeee_nnnn(3N), _tttt______oooo_pppp_eeee_nnnn(3N)
  100.  
  101. DDDDIIIIAAAAGGGGNNNNOOOOSSSSTTTTIIIICCCCSSSS
  102.      _tttt______ssss_nnnn_dddd_dddd_iiii_ssss returns 0 on success and -1 on failure and _tttt______eeee_rrrr_rrrr_nnnn_oooo is set to
  103.      indicate the error.
  104.  
  105.  
  106.  
  107.  
  108.  
  109.  
  110.  
  111.  
  112.  
  113.  
  114.  
  115.  
  116.  
  117.  
  118.  
  119.  
  120.  
  121.  
  122.  
  123.  
  124.  
  125.  
  126.  
  127.  
  128.  
  129.                                                                         PPPPaaaaggggeeee 2222
  130.  
  131.  
  132.  
  133.